Repository navigation
Cut a line of text written after a screenshot's PNG (CHALLENGES 408) - #338
Merged
Merged
Conversation
On the Android Automotive 15 emulator 38 of 39 captures in a trace ended in a FORTIFY warning after IEND, and so did mobium screenshot. Cut, the capture ends at IEND.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On the Android Automotive 15 emulator, screencap wrote "FORTIFY: pthread_mutex_lock called on a destroyed mutex" after the PNG's IEND in 38 of 39 trace screenshots, and in mobium screenshot. Image viewers ignore it; ffmpeg reported every one as damaged. A capture is now cut at IEND when a short line of text follows, the rule CHALLENGES 211 applies to text before it; anything else after it is refused. A car screenshot then ended at IEND. make ci passes.